Skip to main content

Reply to this post | See parent post | Go Back
View Post [edit]

Poster: tracey pooh Date: Jul 9, 2005 3:48am
Forum: movies Subject: Re: Search engine lagging behind

yes, but there are soooooo many updates and soooo frequently that i think this would be prohibitive...

so we use the DB for that (it can handle that kind of update load), and then we designed the SE to take bulk total updates every 3 hours (which it couldn't handle reliably).

but good idea! 8-)

--t

Reply to this post
Reply [edit]

Poster: Madhavananda Date: Jul 9, 2005 3:53am
Forum: movies Subject: Re: Search engine lagging behind

Of course I haven't the singlest clue about your infrastructure... I'm thinking of load-balancing in terms of a single server here, and that probably isn't the environment you're in. In that case, having items calling across the network with each tiny update is of course a no-no.

The concept could be extended to engaging the items in "reporting" to the search engine index at set intervals, whatever the interval might be. Say, calling home every 20 or 50 downloads. Then you wouldn't have items reporting to the SE constantly.

This post was modified by Madhavananda on 2005-07-09 10:53:57

Reply to this post
Reply [edit]

Poster: tracey pooh Date: Jul 10, 2005 4:02am
Forum: movies Subject: Re: Search engine lagging behind

Hi Madhavananda,

well, again, good ideas.
but the Major Issue we have with our Search Engine is that it's decently neglected and not squarely under someone's responsibility here.

So code changes to it, even little ones, take a long time and can be challenging.

So we're mostly trying to stick with whatever the SE has functionality-wise for now, and accommodate around it (since the rest of the backend is much more easily changeable).

Anyway, just thought a little more insight might help as you seem curious and helpful, as always!
8-)

--tracey